Summary

Closes #2997

This PR adds a base integration with Octopus Deploy, allowing users to trigger workflows from deployment events and start release deployments directly from SuperPlane.

Demo

Loom walkthrough: https://www.loom.com/share/acf60dceb634468691c00f8f6a648bb4

Features

Authentication

• API key authentication via the X-Octopus-ApiKey header.
• Supports space-level configuration (custom Space ID or defaults to Spaces-1).

Trigger: On Deployment Event

• Automatically creates Subscriptions in Octopus using the API.
• Uses a unique naming convention (SuperPlane-{webhookID}) to avoid collisions between workflow nodes.
• Verifies X-SuperPlane-Webhook-Secret to ensure payload authenticity.

Action: Deploy Release

• Triggers a deployment for a selected Release and Environment.
• Implements a 30s polling mechanism to track deployment status if webhooks fail or are delayed.
• Provides Success and Failed outputs for conditional workflow branching.

Technical Decisions

1. Polling fallback
   Although Octopus supports task completion webhooks, a polling loop is implemented in the Deploy Release action to prevent workflows from hanging if a webhook is dropped. This aligns with other long-running integrations (e.g., Render).

2. Isolated Subscriptions per trigger node
   Each "On Deployment Event" node creates its own Subscription. This enables granular filtering (e.g., different environments per node) without cross-event noise.

How to Test

Prerequisites

• An Octopus Deploy instance (Cloud or Server).
• ngrok for local webhook testing.

Configure Connection

1. Add a new Octopus connection.

2. Provide:

   • Server URL (e.g., https://example.octopus.app)
   • API Key (generated in Profile → My API Keys)

Test Trigger

1. Add the "On Deployment Event" node.
2. Create a deployment in Octopus.
3. Verify the workflow triggers.

Test Action

1. Add the "Deploy Release" node.
2. Select a Project, Release, and Environment.
3. Run the workflow and confirm the deployment starts in Octopus.